Skip to content

[Docs] Run tests/ops off CUDA under the tileops_test target - #85

Open
lcy-seso wants to merge 1 commit into
tile-ai:mainfrom
lcy-seso:docs/ops-off-cuda
Open

lcy-seso wants to merge 1 commit into
tile-ai:mainfrom
lcy-seso:docs/ops-off-cuda

Conversation

@lcy-seso

@lcy-seso lcy-seso commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

Summary

The development guide lists the tests/ops smoke run under tests.privateuse1.target and the
cuda_only check split between the builtin target and the test target, following
tile-ai/TileOPs#2816.
lcy-seso added a commit to tile-ai/TileOPs that referenced this pull request Nov 2, 2026
…at computes each op's reference (#2816)

## Summary

- Run `tests/ops` smoke tests through a test-only `tileops_test` target
that computes each operator's shared workload reference on PrivateUse1.
- Report unsupported reference calls as explicitly listed `unvalidated`
skips; validate CUDA-only exclusions under the same target.
- Share the op-to-workload registry through `workloads/calls`; keep
benchmark-specific binders, copy accounting and input overrides in
`benchmarks/_cases`.
- Add test-device generators and convolution support, correct test
capability marks, and honor GQA backward scale and empty-row semantics
in the reference.

## Limitations

This target tests backend-independent contracts and test portability.
Comparing shared references does not establish a real backend's
numerical correctness; #2611 remains open. Calls without a usable
reference remain visible as unvalidated.

[Validation
details](#2816 (comment)).
Companion documentation: tile-ai/TileOPs.github.io#85.

Closes #2803

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant